-
-
Notifications
You must be signed in to change notification settings - Fork 445
Fix Home Page Update Issue #3819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This comment has been minimized.
This comment has been minimized.
🥷 Code experts: onesounds Jack251970, onesounds have most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame: ✨ Comment |
Be a legend 🏆 by adding a before and after screenshot of the changes you made, especially if they are around UI/UX. |
📝 WalkthroughWalkthroughThe changes refactor how the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant UI (ResultListBox)
participant Settings
User->>Settings: Change OpenResultModifiers or ShowOpenResultHotkey
Settings->>UI (ResultListBox): OnPropertyChanged notification
UI (ResultListBox)->>UI (ResultListBox): Updates UI via binding and BoolToVisibilityConverter
Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR ensures the home page (results view) updates immediately when changing the result modifier key or toggling the open-result-hotkey visibility.
- Settings properties (
OpenResultModifiers
,ShowOpenResultHotkey
) now raise change notifications - XAML updated to bind directly to
Settings.ShowOpenResultHotkey
with a one-way converter - Main window listens for modifier-key changes to re-query results if on the home page
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
Flow.Launcher/ViewModel/ResultViewModel.cs | Removed the computed ShowOpenResultHotkey property to rely on direct binding |
Flow.Launcher/ResultListBox.xaml | Added BoolToVisibilityConverter resource and switched binding to settings |
Flow.Launcher/MainWindow.xaml.cs | Added case for Settings.OpenResultModifiers to refresh home page queries |
Flow.Launcher.Infrastructure/UserSettings/Settings.cs | Converted two auto-properties into manual properties that fire OnPropertyChanged |
Comments suppressed due to low confidence (3)
Flow.Launcher.Infrastructure/UserSettings/Settings.cs:45
- There’s no test covering the
OpenResultModifiers
change notification and subsequent UI update. Add a unit or integration test to confirm modifying this property triggers the expected re-query behavior on the home page.
public string OpenResultModifiers
Flow.Launcher/ResultListBox.xaml:39
- [nitpick] You now have two different visibility converters (
BoolToVisibilityConverter
andOpenResultHotkeyVisibilityConverter
). Consider consolidating into one to reduce confusion and duplicated logic.
<converter:BoolToVisibilityConverter x:Key="BoolToVisibilityConverter" />
…date Fix Home Page Update Issue
Changes